We are sending RTF Mails over COM using Word and Outlook functions. Here a code snippet of what is done:

        Set objDocument = objWord.Documents.Open(FileName:=strFileName, ReadOnly:=True)
        Set outMailItem = objDocument.MailEnvelope.Item        
        outMailItem.Save
        retEntryId = outMailItem.EntryID

        objOutlook.Application.Session.GetItemFromID(retEntryId )

	If Not objMail Is Nothing Then

            With objMail
                .To = sEmpfnger
                .CC = sEmpfngerCC
                .BCC = sEmpfngerBCC    
                .Subject = KontaktItem.Betreff                
                    .OriginatorDeliveryReportRequested = True
                    .ReadReceiptRequested = True
                .Importance = KontaktItem.Wichtigkeit

              For lngIndex = 1 To lngUBound
                    If FileDirExist(AnhangList(lngIndex)) Then
                        .Attachments.Add AnhangList(lngIndex)         
                    End If
                Next
                .Send  
         End With

One of our customers is using Office 2013 and Exchange 2013 and after installing the latest patches a few weeks ago, he is unable to send any mails containing RTF Text.

Exchange is returning and NDR with the following error:

Remote Server returned '554 5.6.0

STOREDRV.Submit.Exception:TextConvertersException; Failed to process messagedue to a permanent exception with message data truncatedTextConvertersException: data truncated'

Ursprngliche Nachrichtenkpfe:

Received: xxxx  by xxxx with mapi idxxxx; Thu, 25 Jun 2015 13:19:23 +0200
MIME-Version: 1.0
Content-Type: text/plainDate: Thu, 25 Jun 2015 13:19:23 +0200
X-MS-Exchange-Transport-FromEntityHeader: Hosted
Message-ID: <xxxxxxxxx>
Subject: xxxx

It sounds similar as kb/2694566

Any hints as to what might be going wrong here?

It seems the categorizer treats the message as corrupted and blocks the message submission, there's no problem with your code, so that you need to install the latest rollup update for exchange 2013 it will fix this issue.

Thanks for your answer. CU 9 is already installed on the exchange.

It seems to be an outlook problem though, because the problem occurred first on the terminal server Outlook. Then it still worked with a local outlook, until all outlook patches were installed locally too.  Now it doesn't work at all.

Hi Provis,

Base on my search, the client signature may cause the issue also, you can try to remove the signature and check if any helps.

Best regards,

Problem was solved after running windows update today.

Thanks a lot.